Patrick Elliott wrote:
> So.. The question becomes, knowing what I need, how the bloody heck 
> do you implement it?

I would say you can separate the security from the calculations pretty 
easily.

1) The client knows what it's drawing at each pixel, so when you click, 
compute which bit of mesh was shown in the pixel the mouse was in when 
the click occurred. Report that to the server.

2) All the *server* has to do is verify that the client is capable of 
seeing the bit of mesh that you clicked on. In other words, the server 
doesn't have to figure out where you clicked - it only has to confirm 
that you could have clicked on what the client figured out. Given the 
server knows the object's mesh coords and the camera's location, this 
should be pretty easy. A piece of mesh partially obscured might make 
this a little harder.

> Basically, I am going to try to propose an extension to the "touch" 
> functions in a virtual environment, which works similar to the image 
> maps used in HTML pages (so you can make images/buttons on the texture 
> as target points), 

Yeah. My object in SL took 57 objects to make a 5x5 board for 2 people. 
Messy to instantiate. :-)


-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."

Post a reply to this message